app/components/Changelog/Card.vue (1)

24-27: ⚡ Quick win

Drop the non-null assertion on inject and supply a safe default.

inject<{...}>('changelog-provider-linkattr')! only affects TypeScript; if any future caller (tests, Storybook, another consumer) renders Card.vue without the parent providing 'changelog-provider-linkattr', the destructuring will throw at runtime. Either provide a default object or guard the destructuring so the card degrades gracefully.

♻️ Suggested refactor

-const { providerIcon, viewOnProvider } = inject<{
-  providerIcon: ComputedRef<IconClass>
-  viewOnProvider: ComputedRef<string>
-}>('changelog-provider-linkattr')!
+const injected = inject<{
+  providerIcon: ComputedRef<IconClass>
+  viewOnProvider: ComputedRef<string>
+} | null>('changelog-provider-linkattr', null)
+const providerIcon = computed(() => injected?.providerIcon.value)
+const viewOnProvider = computed(() => injected?.viewOnProvider.value)

You can then v-if="providerIcon" around the LinkBase to skip rendering when the context is absent.

Also consider using a typed InjectionKey<...> exported from a shared module instead of a raw string — it removes the need to repeat the generic at every call site and prevents key drift between provider and consumer.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@app/components/Changelog/Card.vue` around lines 24 - 27, The inject call in
Card.vue uses a non-null assertion (inject<...>('changelog-provider-linkattr')!)
which can throw at runtime if the provider is missing; change it to supply a
safe default or guard the result before destructuring: call
inject('changelog-provider-linkattr') without the bang, check for null/undefined
and fall back to a default object providing safe ComputedRefs for providerIcon
and viewOnProvider, then only render the LinkBase when providerIcon is present
(e.g., v-if="providerIcon"); optionally replace the raw string key with an
exported typed InjectionKey to keep provider/consumer keys consistent
(referencing providerIcon, viewOnProvider, inject, and
'changelog-provider-linkattr').

app/pages/package-changelog/[[org]]/[name].vue (2)

141-185: ⚡ Quick win

Remove the commented-out <Suspense> block instead of leaving it inline.

Per the PR objectives the Suspense-based loading was intentionally replaced with useLazyFetch's pending inside ChangelogReleases/ChangelogMarkdown. Leaving ~45 lines of commented template (lines 141–185) creates noise, hides the actual control flow (the v-if/v-else-if chain reads awkwardly with comments interleaved), and will rot quickly. Git history is sufficient for recovery.

♻️ Suggested cleanup

-      <!-- <Suspense v-else-if="changelog"> 
-        <template `#default`>-->
-      <LazyChangelogReleases
+      <LazyChangelogReleases
         v-if="changelog?.type === 'release'"
         :info="changelog"
@@
         />
       </LazyChangelogMarkdown>
-      <!-- </template>
-        <template `#fallback`>
-          <section class="flex flex-col gap-2 py-3">
-            <SkeletonBlock class="h-8 w-40 rounded" />
-            <ul class="ms-3 list-disc my-[1rem] ps-[1.5rem] marker:color-border-hover">
-              <li class="mb-1" v-for="_n in 5">
-                <SkeletonBlock class="h-7 w-full max-w-2xl rounded" />
-              </li>
-            </ul>
-
-            <SkeletonBlock class="h-5 w-5/6 max-w-2xl rounded" />
-            <SkeletonBlock class="h-5 w-3/4 max-w-2xl rounded" />
-          </section>
-        </template>
-      </Suspense> -->
       <!-- error handling -->

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@app/pages/package-changelog/`[[org]]/[name].vue around lines 141 - 185,
Remove the large commented-out Suspense block and its inner fallback template so
the template contains only the active v-if/v-else-if chain; delete the commented
"<Suspense> ... </Suspense>" section wrapping (and any commented fallback
markup) that surrounds the LazyChangelogReleases and LazyChangelogMarkdown
usage, leaving the LazyChangelogReleases, LazyChangelogMarkdown and their
LazyChangelogErrorMsg children intact; ensure no other logic relies on that
Suspense wrapper (the components ChangelogReleases/ChangelogMarkdown now handle
loading via useLazyFetch pending) and run a quick lint/format pass to confirm
the template remains valid.

---

151-170: 💤 Low value

Rename viewOnGit prop to viewOnProvider in ChangelogErrorMsg component for consistency.

The variable was renamed to generic provider terminology in line 51 (viewOnProvider), but the component's prop on lines 154 and 168 still uses :viewOnGit="viewOnProvider". Update the prop name in app/components/Changelog/ErrorMsg.vue to maintain uniform abstraction.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@app/pages/package-changelog/`[[org]]/[name].vue around lines 151 - 170, The
Changelog error component still defines/accepts the old prop name viewOnGit
while callers (LazyChangelogErrorMsg) pass viewOnProvider; open
app/components/Changelog/ErrorMsg.vue and rename the prop from viewOnGit to
viewOnProvider (keep the same type/default/behavior), update any internal
references in the component (props destructuring, template bindings, methods) to
use viewOnProvider, and ensure the component export/props declaration matches
the new name so the usages at lines where LazyChangelogErrorMsg is rendered work
consistently.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes